home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.cs.arizona.edu
/
ftp.cs.arizona.edu.tar
/
ftp.cs.arizona.edu
/
icon
/
newsgrp
/
group94a.txt
/
000066_icon-group-sender _Sun Feb 27 05:51:21 1994.msg
< prev
next >
Wrap
Internet Message Format
|
1994-08-19
|
1KB
Received: by cheltenham.cs.arizona.edu; Wed, 2 Mar 1994 10:46:14 MST
Date: 27 Feb 94 05:51:21 GMT
From: agate!howland.reston.ans.net!noc.near.net!news.delphi.com!usenet@ucbvax.Berkeley.EDU (Will Mengarini)
Organization: Delphi (info@delphi.com email, 800-695-4005 voice)
Subject: Re: file dates
Message-Id: <5a-oml5.mengarini@delphi.com>
References: <1994Feb23.121210.9747@hemlock.cray.com>
Sender: icon-group-request@cs.arizona.edu
To: icon-group@cs.arizona.edu
Status: R
Errors-To: icon-group-errors@cs.arizona.edu
I've been doing MS-DOS-specific utilities for this kind of thing,
but I think this is a very good point that it'd be useful
for the language to define keywords or functions for things
that can reasonably be expected to be present on most or all
implementations.
Can anybody name an Icon implementation for a system where
files are created & stored in a way that doesn't keep track
of both creation date & time, & last-change date & time?
It would make sense for this to be a library capability
rather than a language capability, but then the icode
on a particular system should contain only the code for handling
that system, which wouldn't be the case if the system were
identified using a conditional expression based on &features.
I use IPP (an Icon preprocessor from BIPL) in all my programs,
but I'd expect most Unix people to use M4, which is incompatible.
Does anybody else have any relevant thoughts on preprocessing?